home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Experimental BBS Explossion 3
/
Experimental BBS Explossion III.iso
/
gus
/
sdkdigv8.zip
/
SDKV8N15.TXT
< prev
next >
Wrap
Text File
|
1994-01-17
|
3KB
|
79 lines
Apparently-To: john.smith@gravis.com
GUS Programmer's Digest Mon, 17 Jan 94 4:00 Volume 8: Issue 15
Today's Topics:
Envelope Offsets not at zero
Mod to 669 converter
Standard Info:
- Meta-info about the GUS can be found at the end of the Digest.
- Before you ask a question, please READ THE FAQ.
----------------------------------------------------------------------
Date: Sun, 16 Jan 1994 05:59:43 -0600 (CST)
From: Jason William Whiteman <jww9624@tamsun.tamu.edu>
Subject: Re: Envelope Offsets not at zero
> fouling up. An offset of 8 does mean 8, so don't set the ramp's
> endpoint to 0. 8 is effectively silent anyway, and when it's
> reached, the volume can be set directly to 0 without causing a pop.
The pseudo-code supplied should have made it clear that the
ramp would not go to zero. In the case of an offset of 8, the code
would have said "ok, it's under the threshold of 10, so don't add the
base_volume to the offset (base volume=volume when patch is started)."
I am taking the envelope offset values to be an addative value (always
with respect to the initial volume) unless the envelope offset is
below a threshold point. Because you cannot add any positive value
(unsigned char) to the initial volume and get silence (or near-silence),
I implemented this conditional nature of looking at offsets. However,
if I think of the envelope offsets as a multiplying process, instead of
and addative process, one formula could handle any offset value. The
point is: I just do not know.. A possible multiplying method: take the
current volume and ramp to [ cur. vol * ( env_offset / 255 ) ].
This way, the next envelope's volume level would never be above the
initial volume of the patch. Perhaps this is correct?
I appreciate the response. The wording tended to imply a
geometric nature to envelope values.
> Phat.
Jason Whiteman
------------------------------
Date: Mon, 17 Jan 1994 10:36:46 +1030 (CST)
From: Gavin <SCARMAN@hfrd.dsto.gov.au>
Subject: Re: Mod to 669 converter
>Does anyone have/seen a .MOD to .669 converter?
Yes but it does a poor job with tempo changes. I don't have a 669 editor so I've
never seen whether these can be fixed. If you want it I can send it uuencoded if
you'll promise to upload it to epas, I got it from a BBS.
------------------------------
End of GUS Programmer's Digest V8 #15
*************************************
To post to tomorrow's digest: <gus-sdk@dsd.es.com>
To (un)subscribe or get help: <gus-sdk-request@dsd.es.com>
To contact a human (last resort): <gus-sdk-owner@dsd.es.com>
FTP sites: archive.epas.utoronto.ca /pub/pc/ultrasound
wuarchive.wustl.edu /systems/ibmpc/ultrasound
archive.orst.edu /pub/packages/gravis
theoris.rz.uni-konstanz.de /pub/sound/gus
nctuccca.edu.tw /PC/ultrasound
FTP mail server: mail-server@nike.rz.uni-konstanz.de
Hints:
- Get the FAQ from the FTP sites or the request server.
- Mail to <gus-sdk-request@dsd.es.com> for info about other GUS
related mailing lists (general use, musician's, etc.).